Skip to content

fix: parse tracebacks after stderr prefixes#323

Open
alceops wants to merge 1 commit intoextrabacon:masterfrom
alceops:fix-parse-prefixed-traceback
Open

fix: parse tracebacks after stderr prefixes#323
alceops wants to merge 1 commit intoextrabacon:masterfrom
alceops:fix-parse-prefixed-traceback

Conversation

@alceops
Copy link
Copy Markdown

@alceops alceops commented Apr 28, 2026

Summary

  • parse Python tracebacks even when stderr contains prefix log lines before the traceback header
  • keep the parsed traceback focused on the traceback block
  • add a regression fixture/test for prefixed stderr output

Validation

  • npm ci
  • npm test -- --grep "parseError|prefixed logs" (4 passing)

Fixes #309.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The error object doesn't have Error & traceback properties.

1 participant